I have just installed MOSS 2007 on a machine with 64-bit Win 2K3. It installs fine but after installation navigating to the Central Administration site yields a "Service Unavailable" message. I tried searching for reasons for this, but the event viewer has no significant logs, and the relevant services (World Wide Wed Publishing Service, Windows SharePoint Services Administration, and Windows SharePoint Services Timer are all started. I had previously installed and run MOSS 2007 successfully on this machine, but had to uninstall and reinstall for an unconnected reason. After reinstalling, I am now getting the "Service Unavailable" error. Can someone give me an idea what to look into to debug this issue? Thanks in advance.

My guess is that you have changed a pw. However, there are three things which may have caused the issue which are documented here: http://support.microsoft.com/kb/823552 Regards, Todd Booth

Greetings, I also had this "Service Unavailable" problem, and I finally "fixed" it. I was migrating my Exchange 2003 / LCS 2005 machine to a 64-bit W2K3 Exchange 2007 / OCS 2007 machine. I installed Exchange 2007 without a problem, and everything worked fine. Whenever I installed OCS 2007, immediately after the installation completed successfully, IIS would still seem to be working, but as soon as a client would try to access any webpage on it ( OWA, for example ), IIS would reply a "Service Unavailable". I found out the two reasons for this: 1 - I forgot to "Allow" the Active Server Pages, in IIS->Server->Web Service Extensions, which is required for OCS 2007; 2 - IIS 6.0 on a W2K3 SP1 machine works in either full 64-bit mode, or a 32-bit on 64-bit mode (WOW64). Exchange 2007 needs it to be in 64-bit for it's web services, while OCS 2007 needs it to be WOW64... I ended up separating the two services into two different boxes, one 64-bit for Exchange, and one 32-bit for OCS.I hope this helps someone Rodrigo Monteiro

Moving the whole thread to setup/*Administration* which is where it seems to belong.

Hi Rodrigo, I think I have the same problem you had. I've tried to build a combined Ex2007 + OCS 2007 server and hit the same issue. Like you I think I will have to put the services on 2 seperate boxes. Did you manage to salvage your Exchange 2007 installation? I have removed OCS 2007 from the 64bit server but the issue of Service Unavailable is still there. Did you manage to fix this and if so how? Thanks for any help, Marcus

I had this error and the reason was that the identity that ran the app pool for this website in IIS was locked. I got the domain account unlocked and Central Admin came back online. Regards, Manoj

If you have made any change on service accounts, remember to do an IISRESET. Event though you go to IIS Admin services and change, it would fail again to start. Just IISRESET, after that if should be working. Regards. DavidDavid Bernal Manero MCTS MOSS2007 / MCTS WSS3 MCTS MOSS2010

Is the app pool account a member of the local IIS_WPG group? "deibeat" wrote in message news:e51d4847-21a8-4b57-a6cb-778a23791cf0... If you have made any change on service accounts, remember to do an IISRESET. Event though you go to IIS Admin services and change, it would fail again to start. Just IISRESET, after that if should be working. Regards. David David Bernal Manero MCTS MOSS2007 / MCTS WSS3 MCTS MOSS2010